First visit
CO2 0.056g
SIZE 179.1 KB
Return visit
CO2 0.003g
SIZE 10.99 KB
Emissions calculator
40%
60%
Total: per month
This is equivalent to: Driving miles in a Tesla Model S Watching hours of Netflix (in HD)
At least trees would be needed to offset the CO2 in a year
Page breakdown
Type
Requests
Size
CO2
Document
1
9.43 KB
0.003g
Image
15
120.28 KB
0.037g
Stylesheet
1
4.96 KB
0.002g
Script
6
41.39 KB
0.013g
XHR
3
3.03 KB
0.001g
History
Date
CO2
Size
25.Sep.2024
0.056g
179.1 KB
27.Jun.2024
0.039g
125.8 KB
15.May.2024
0.040g
130.23 KB
27.Mar.2024
0.036g
117.17 KB
06.Sep.2023
0.044g
141.15 KB
22.Apr.2023
0.103g
138.63 KB
22.Apr.2023
0.165g
222.85 KB
22.Apr.2023
0.077g
103.99 KB
22.Apr.2023
0.105g
141.71 KB
22.Apr.2023
0.106g
142.84 KB
19.Apr.2023
0.148g
199.54 KB
This website has been tested 30 times**
Previous 10 test results are displayed above.
Core Web Vitals
Max Potential First Input Delay
20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Learn more about the Maximum Potential First Input Delay metric
Largest Contentful Paint
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
JavaScript execution time
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Initial server response time was short
Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it.
Avoids enormous network payloads
Total size was 179 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Speed Index
0.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Time to Interactive
0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Serve static assets with an efficient cache policy
1 resource found
A long cache lifetime can speed up repeat visits to your page.
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance.
Minimizes main-thread work
0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Serve images in next-gen formats
Potential savings of 10 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Avoids an excessive DOM size
267 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance.
Reduce unused JavaScript
Potential savings of 20 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
First Contentful Paint
0.3 s
First Contentful Paint marks the time at which the first text or image is painted.
Notes
* These are assets not hosted on the same domain e.g. tracking scripts, iframe embeds, or files hosted on a CDN.
** This was only counted from 11.Apr.2021.
These measurements are for each new visitor, for returning visitors the footprint would be lower based on caching mechanisms.
Our brackets for the ratings: